Skip to content

Add settings to launch debugger on test failure#7318

Merged
Evangelink merged 3 commits intomainfrom
dev/amauryleve/debugger-launch
Feb 6, 2026
Merged

Add settings to launch debugger on test failure#7318
Evangelink merged 3 commits intomainfrom
dev/amauryleve/debugger-launch

Conversation

@Evangelink
Copy link
Member

Fixes #2033.

I have thought about having this as a platform feature but there is really few code to add. Besides, it would need to be introduced through a new mechanism as the message bus we are using could result in the debugger launch being triggered pretty far from the time of error.

Copy link

@aha8med7788-svg aha8med7788-svg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nohwnd
Copy link
Member

nohwnd commented Feb 2, 2026

Will the debugger launch block in non-interactive session / interactive ci session? Maybe you want to detect CI and not do it.

@Evangelink
Copy link
Member Author

Will the debugger launch block in non-interactive session / interactive ci session? Maybe you want to detect CI and not do it.

It was part of open questions I had when discussing with @Youssef1313, I have updated the setting to use an enum so we could skip but also force running on CI. It already happened that I had issue on CI and being able to debug CI was helpful.

@Evangelink Evangelink enabled auto-merge February 6, 2026 16:13
@Evangelink Evangelink merged commit 7ed7158 into main Feb 6, 2026
10 checks passed
@Evangelink Evangelink deleted the dev/amauryleve/debugger-launch branch February 6, 2026 19:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Option to launch debugger on test failure

4 participants